‎AbstractCompilerMojo::execute should propagate exception cause

In ‎AbstractCompilerMojo::execute, errors caught from the compiler manager are swallowed, instead a new MojoExecutionException is thrown. This renders debugging root causes for problems with compiler DI scanning, injection and instantiation virtually impossible.

The caught exception should be passed on as a cause for the new exception.

laeubi, see our discussion here.